-
Notifications
You must be signed in to change notification settings - Fork 157
chore(ALL): fix packaging #316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
34c8936
to
a0e58d6
Compare
86a8b7d
to
14e7eb4
Compare
@@ -12,7 +12,7 @@ | |||
"parserOptions": { | |||
"ecmaVersion": 2020, | |||
"sourceType": "module", | |||
"project": "./tsconfig.json" | |||
"project": "./tsconfig-dev.json" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not disagreeing, just curious: why do we need a tsconfig-dev vs prod?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I explained it in pr details but basically we need one for eslint and for packaging to get everything lint but just src packaged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great but I am concerned that moving folders around now will overwrite some of the changes that are being done in other PRs and already merged from other packages
it's not compulsory to move types but it makes final package a lot cleaner from my point of view. if it's too much of a refacto I can change it back but I'll need a bit of time tomorrow to do so |
Description of your changes
Current dependency tree makes it hard to package cleanly.
After isolating LambdaInterface in a dedicated shared package (#314) we can now rely on this package and have a clean npm.
Some details on the changes:
tsconfig-dev.json
to make sure all folders get linted but only src get packaged.lib/src/index.js
andlib/type/index.js
butlib/index.js
)/types/
in coverage because it's not recognized as covered by jest.How to verify this change
Related issues, RFCs
#136
PR status
Is this ready for review?: YES
Is it a breaking change?: NO
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.